Repository navigation
Clarify that repeatable CLI arguments are appended to config file values - #621
Conversation
K3s inserts config file values ahead of the CLI arguments, and repeatable flags append each occurrence, so values from both sources are combined rather than the CLI replacing the list. Fixes k3s-io#620 Signed-off-by: Ryan02I5 <209603985+Ryan02I5@users.noreply.github.com>
|
Local run of the repository's CI steps on this branch (the workflows are waiting for approval here):
The external link check was not run locally. |
Use the reviewer's wording for how repeatable CLI arguments combine with configuration file values, and add an example to the Value Merge Behavior section. Signed-off-by: Ryan02I5 <209603985+Ryan02I5@users.noreply.github.com>
|
Thanks @dereknola. I applied your suggestion and added your example to the Value Merge Behavior section in 8169019 (with For reference, this matches The failing "Test Links" check comes from an external link in |
Continue the foo/bar/other label keys from the examples above, and describe how the kubelet resolves duplicate label keys. Signed-off-by: Ryan02I5 <209603985+Ryan02I5@users.noreply.github.com>
Signed-off-by: Ryan02I5 <209603985+Ryan02I5@users.noreply.github.com>
Fixes #620
The Configuration File section says repeatable CLI arguments overwrite all values in the list. K3s actually combines them:
configfilearginserts the config file values ahead of the CLI arguments.This was reproduced on v1.37.2+k3s1 with
--disable; #620 has the details.This changes only the English page. The zh and ja translations contain the same sentence.